This class now uses JUnit Jupiter's @AfterEach but still appears to rely on JUnit 4 annotations/imports elsewhere (e.g., org.junit.Before, @Category, etc.). Mixing JUnit 4 and JUnit 5 lifecycle annotations can result in setup/teardown methods not running (depending on which engine executes the test). Please migrate the remaining JUnit 4 annotations to JUnit Jupiter equivalents (e.g., @BeforeEach, @AfterAll, @Tag) or keep the class purely JUnit 4 (use @After).

The test method for the JSON response is still named testGetUnkownServers (typo: missing 'n' in 'Unknown'). Consider renaming it to testGetUnknownServers for consistency with the HTML variant and to improve readability/searchability.

import static org.mockito.Mockito.any; is not the correct matcher import (matchers live under org.mockito.ArgumentMatchers). This will not compile and also makes the intent less clear. Switch the static import to org.mockito.ArgumentMatchers.any (or use anyString/any(Class) as appropriate).

This test uses @ExtendWith(MockitoExtension.class) but also calls MockitoAnnotations.openMocks(this) in @BeforeEach. That creates a second Mockito session and reinitializes the @Mock fields, which can lead to confusing behavior and unnecessary resources. Remove the manual openMocks call and let MockitoExtension manage mock initialization (or drop the extension and keep manual initialization, but not both).